The Cassandra Server must be able to generate audit records when security objects are accessed.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-72693 | VROM-CS-000265 | SV-87325r1_rule | Medium |
| Description |
|---|
| Changes to the security configuration must be tracked. This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE |
| STIG | Date |
|---|---|
| vRealize - Cassandra Security Technical Implementation Guide | 2017-06-06 |
Details
| Check Text ( C-72849r1_chk ) |
|---|
| Review the Cassandra Server configuration to ensure audit records are generated when security objects are accessed. At the command prompt, execute the following command: # grep ' If level is not set to "ALL", this is a finding. |
| Fix Text (F-79097r1_fix) |
|---|
| Configure the Cassandra Server to generate audit records when security objects are accessed. At the command line execute the following command: # sed -i 's/^\(\s*\) |